xen init script: Do nothing if running for wrong Xen package
authorIan Jackson <ian.jackson@citrix.com>
Thu, 7 Feb 2019 15:56:49 +0000 (15:56 +0000)
committerIan Jackson <ian.jackson@citrix.com>
Fri, 22 Feb 2019 14:00:16 +0000 (14:00 +0000)
commitcc85504103f39ab5e7bd26de5994ed5767cba23a
treedd1c0a03fd390768c130fcbaf126454c7b742020
parent194dd19af2f4ebe29b135c3f839dfcb3b6acba2e
xen init script: Do nothing if running for wrong Xen package

See the big comment.  We think that this is responsible for various
bugs and, particularly, reports of mysteriously missing xenconsoled.

For example, this bug would mean that after a Xen version upgrade,
autoremoval of an obsolete xen-utils-V package would stop the running
xenconsoled.  This is obviously awkward to track down, and could occur
many weeks or months after the upgrade.

Closes: #851654
Signed-off-by: Ian Jackson <ian.jackson@citrix.com>
Acked-by: Hans van Kranenburg <hans@knorrie.org>
debian/xen-utils-common.xen.init